Triple
T20784087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corona Graeca |
E511582
|
entity |
| Predicate | hasPositionInCrown |
P52685
|
FINISHED |
| Object | lower part |
—
|
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: lower part | Statement: [Corona Graeca, hasPositionInCrown, lower part]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInCrown Context triple: [Corona Graeca, hasPositionInCrown, lower part]
-
A.
crownPosition
chosen
Indicates the relative placement or orientation of a crown with respect to another object or reference point.
-
B.
hasCrownCount
Indicates the number of crowns that an entity possesses or is associated with.
-
C.
hasCrownName
Indicates that an entity possesses or is identified by a specific crown name, typically used as an official or regal title.
-
D.
hasCrownGroup
Indicates that an entity belongs to, or is classified within, the crown group (the clade consisting of a common ancestor and all its living descendants) of another specified lineage or taxonomic group.
-
E.
crownContains
Indicates that a crown includes or holds within it a specified object, element, or component.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28a4584819084d2d02febe47001 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.