Triple
T35018713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nambé people |
E1010129
|
entity |
| Predicate | hasArtisticReputationFor |
P49102
|
FINISHED |
| Object | distinctive arts |
—
|
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: distinctive arts | Statement: [Nambé people, hasArtisticReputationFor, distinctive arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticReputationFor Context triple: [Nambé people, hasArtisticReputationFor, distinctive arts]
-
A.
hasArtisticReputation
chosen
Indicates that an entity is recognized or regarded for its artistic skill, contribution, or standing.
-
B.
hasArtisticAssociationWith
Indicates a relationship in which two entities are connected through shared, collaborative, or thematically related artistic work or influence.
-
C.
hasFamousArtwork
Indicates that an entity possesses or is associated with a well-known or widely recognized artwork.
-
D.
hasArtistOfNotableWork
Indicates that an entity is associated with the artist who created a notable work related to that entity.
-
E.
isFamousWorkOf
Indicates that one entity is a well-known or widely recognized work created by another entity (typically an artist, author, or creator).
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:01 p.m.