Triple
T34349443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taromenane |
E881523
|
entity |
| Predicate | hasContactStatus |
P128885
|
FINISHED |
| Object | voluntarily isolated |
—
|
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: voluntarily isolated | Statement: [Taromenane, hasContactStatus, voluntarily isolated]
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 (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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.