Triple
T36286400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tagaeri |
E893095
|
entity |
| Predicate | contactStatus |
P128885
|
FINISHED |
| Object | uncontacted |
—
|
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: uncontacted | Statement: [Tagaeri, contactStatus, uncontacted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactStatus Context triple: [Tagaeri, contactStatus, uncontacted]
-
A.
communicationStatus
Indicates the current state or condition of a communication process or exchange between entities (e.g., pending, active, failed, completed).
-
B.
interactionStatus
Indicates the current state or condition of an interaction or exchange occurring between entities.
-
C.
hasContactState
chosen
Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with another entity.
-
D.
addresseeStatus
Indicates the role, condition, or state of the entity that is the recipient or target of a communication or action.
-
E.
registrationStatus
Indicates the current state or condition of an entity’s enrollment or registration within a given system or process.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0124a5d7848190a6b56d18db2f661d |
completed | May 11, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_6a01243da1808190ada3ce553e3f55b6 |
completed | May 11, 2026, 12:35 a.m. |
Created at: May 3, 2026, 4:09 p.m.