Triple
T29401543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Sunrise |
E745655
|
entity |
| Predicate | hasComponentField |
P202236
|
FINISHED |
| Object | Sunrise field |
—
|
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: Sunrise field | Statement: [Greater Sunrise, hasComponentField, Sunrise field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentField Context triple: [Greater Sunrise, hasComponentField, Sunrise field]
-
A.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
-
B.
hasComponentForm
Indicates that one entity exists as a structural or compositional form or variant of another entity.
-
C.
hasFieldContribution
Indicates that an entity has made a contribution or provided input within a particular field, domain, or area of activity.
-
D.
hasDefinitionComponent
Indicates that something includes a specific part or element as a component of its overall definition.
-
E.
hasCompanionField
Indicates that an entity is associated with another entity that serves as its companion or complementary field.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0064f8efa48190956287f548a8057d |
completed | May 10, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_6a006471e75c8190adae99bd75e7411b |
completed | May 10, 2026, 10:56 a.m. |
| PDg | Predicate description generation | batch_6a0064f8496081908ac3bb4c53ed08aa |
completed | May 10, 2026, 10:59 a.m. |
Created at: April 28, 2026, 2:51 p.m.