Triple
T16395871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin cross |
E398176
|
entity |
| Predicate | hasLowerPart |
P123258
|
FINISHED |
| Object | longer arm below intersection |
—
|
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: longer arm below intersection | Statement: [Latin cross, hasLowerPart, longer arm below intersection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerPart Context triple: [Latin cross, hasLowerPart, longer arm below intersection]
-
A.
hasUpperPartFrom
Indicates that an entity includes, incorporates, or is composed of an upper part originating from another entity.
-
B.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
C.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
D.
hasLowerDeckFunction
Indicates that an entity serves a specific role or performs a designated function on the lower deck of a structure or vehicle.
-
E.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326462298819087091dc935f0f916 |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.