Triple
T16395870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin cross |
E398176
|
entity |
| Predicate | hasTopPart |
P35
|
FINISHED |
| Object | shorter arm above 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: shorter arm above intersection | Statement: [Latin cross, hasTopPart, shorter arm above intersection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopPart Context triple: [Latin cross, hasTopPart, shorter arm above intersection]
-
A.
hasTopBody
Indicates that one entity possesses or is characterized by a primary upper body section.
-
B.
hasUpperPartFrom
Indicates that an entity includes, incorporates, or is composed of an upper part originating from another entity.
-
C.
hasTopConstruction
Indicates that one entity serves as the uppermost structural element or construction positioned on top of another entity.
-
D.
isToppedWith
Indicates that one entity serves as a topping placed on the surface of another entity.
-
E.
hasPart
chosen
Indicates that one entity is a component, segment, or constituent part 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_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. |
Created at: April 10, 2026, 5:09 a.m.