Triple
T14796824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aduana |
E347801
|
entity |
| Predicate | hasIdentityMarker |
P2130
|
FINISHED |
| Object | clan praise names |
—
|
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: clan praise names | Statement: [Aduana, hasIdentityMarker, clan praise names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentityMarker Context triple: [Aduana, hasIdentityMarker, clan praise names]
-
A.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
B.
hasIdentityComponent
Indicates that an entity includes or is associated with a specific component that contributes to or defines its identity.
-
C.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
D.
hasDistinctIdentity
Indicates that an entity possesses its own unique, distinguishable identity separate from other entities.
-
E.
hasGlobalIdentity
Indicates that an entity possesses a unique, overarching identity that is recognized or valid across multiple systems, contexts, or domains.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5fdd548190a2ee5e668c2b20b4 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.