Triple
T7002918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mongkhon |
E162379
|
entity |
| Predicate | notToBe |
P73536
|
FINISHED |
| Object | placed on the ground |
—
|
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: placed on the ground | Statement: [mongkhon, notToBe, placed on the ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notToBe Context triple: [mongkhon, notToBe, placed on the ground]
-
A.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
B.
isSupposedToBe
Indicates that something is expected or intended to have a particular state, quality, or role, whether or not it actually does.
-
C.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
-
D.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
-
E.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc12af788190b3d06ffc46568410 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c575f081908b43d95d1d99b1a4 |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:33 p.m.