Triple
T35184302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Grande Pyramid |
E1015941
|
entity |
| Predicate | hasDistinctiveProfile |
P18160
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rio Grande Pyramid, hasDistinctiveProfile, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctiveProfile Context triple: [Rio Grande Pyramid, hasDistinctiveProfile, true]
-
A.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
B.
hasDistinctFeature
chosen
Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
-
C.
usesProfile
Indicates that one entity employs, operates under, or is associated with a particular profile in performing its actions or functions.
-
D.
isDistinctiveGivenNameOf
Indicates that a given name uniquely and distinctively identifies or characterizes a particular entity compared to others.
-
E.
hasDistinctiveVoice
Indicates that an entity possesses a voice that is notably unique or easily distinguishable from others.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 3, 2026, 4:02 p.m.