Triple
T35436820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K |
E1024231
|
entity |
| Predicate | placedBeforeAmount |
P194103
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [K, placedBeforeAmount, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placedBeforeAmount Context triple: [K, placedBeforeAmount, true]
-
A.
positionBefore
Indicates that one entity occurs or is arranged earlier in order or sequence than another entity.
-
B.
previousStandardAmount
Indicates the amount or value that was in effect under the immediately preceding standard or baseline before the current one.
-
C.
hasSmallerAmountThan
Indicates that the quantity or amount associated with one entity is less than the quantity or amount associated with another entity.
-
D.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
E.
previouslyPlacedInOrder
Indicates that an item or entity has already been included in a prior order before the current context or transaction.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: May 3, 2026, 4:04 p.m.