Triple
T30302375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lions |
E770684
|
entity |
| Predicate | hasTwinPeaks |
P73388
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Lions, hasTwinPeaks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTwinPeaks Context triple: [The Lions, hasTwinPeaks, yes]
-
A.
hasTwinPeak
chosen
Indicates that an entity possesses or is characterized by two prominent, closely associated peaks or summits.
-
B.
hasTwin
Indicates that one entity is a twin of another, sharing the same birth event or time with a sibling.
-
C.
hasTwinStatus
Indicates that an entity has a twin relationship or classification, such as being one of a pair of twins or having an associated twin counterpart.
-
D.
hasTwinFeature
Indicates that two entities share an identical or nearly identical feature, characteristic, or component, as if they are twins in that respect.
-
E.
hasTwinSatellite
Indicates that one celestial body possesses a satellite that is paired with another satellite in a twin or closely matched relationship.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813b03c881909786514932f103f3 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:49 p.m.