Triple
T38263169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warehouse No.1 |
E1017980
|
entity |
| Predicate | isLocatedBeside |
P44955
|
FINISHED |
| Object | Warehouse No.2 |
—
|
NE NERFINISHED |
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: Warehouse No.2 | Statement: [Warehouse No.1, isLocatedBeside, Warehouse No.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedBeside Context triple: [Warehouse No.1, isLocatedBeside, Warehouse No.2]
-
A.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
B.
situatedNextTo
chosen
Indicates that one entity is located immediately beside another, with no significant separation between them.
-
C.
locatedInOrAdjacentTo
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
-
D.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
E.
isBSideOf
Indicates that one entity is located on the B side or secondary face of another entity, typically in a two-sided or dual-orientation context.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4:30 p.m.