Triple
T34349443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taromenane |
E881523
|
entity |
| Predicate | hasContactStatus |
—
|
GENERATED |
| Object | voluntarily isolated |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactStatus Context triple: [Taromenane, hasContactStatus, voluntarily isolated]
-
A.
hasContactState
chosen
Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with another entity.
-
B.
hasContactMethod
Indicates that an entity has a specific way or channel through which it can be contacted.
-
C.
communicationStatus
Indicates the current state or condition of a communication process or exchange between entities (e.g., pending, active, failed, completed).
-
D.
hasContactType
Indicates the specific kind or category of contact relationship that exists between two entities.
-
E.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
- F. None of above.
Provenance (1 batch)
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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:58 a.m.