Triple
T3176169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meridian Gate |
E66469
|
entity |
| Predicate | sidePassagesUsedBy |
P22634
|
FINISHED |
| Object | civil and military officials |
—
|
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: civil and military officials | Statement: [Meridian Gate, sidePassagesUsedBy, civil and military officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sidePassagesUsedBy Context triple: [Meridian Gate, sidePassagesUsedBy, civil and military officials]
-
A.
numberOfPassages
Indicates the total count of distinct passages associated with or contained within a given entity or context.
-
B.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
C.
extendedPassagesFrom
Indicates that one text or document contains longer or more detailed passages derived from, elaborating on, or continuing the content of another source.
-
D.
areUsedBy
chosen
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
E.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69b0bec8190957913b44d876079 |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.