Triple
T30002081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niōmon gate |
E762195
|
entity |
| Predicate | marksThresholdOf |
P49185
|
FINISHED |
| Object | Buddhist temple precincts |
—
|
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: Buddhist temple precincts | Statement: [Niōmon gate, marksThresholdOf, Buddhist temple precincts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksThresholdOf Context triple: [Niōmon gate, marksThresholdOf, Buddhist temple precincts]
-
A.
thresholdFor
Indicates that one entity specifies the minimum or limiting value at which a condition, effect, or state involving another entity begins to occur or change.
-
B.
passMark
Indicates that an entity has achieved a score or performance level that meets or exceeds the required threshold for passing.
-
C.
marksDetermine
Indicates that one entity’s marks or scores determine or decisively influence the outcome, status, or classification of another entity.
-
D.
closureThreshold
Indicates the limit or boundary value at which a process, operation, or state is considered complete or closed.
-
E.
marksBoundaryIn
chosen
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
- F. None of above.
Provenance (3 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794fa4008190bd8861c7934bf8fe |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:41 p.m.