Triple
T3099164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | angel |
E64672
|
entity |
| Predicate | canInteractWith |
P3970
|
FINISHED |
| Object | humans |
—
|
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: humans | Statement: [angel, canInteractWith, humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canInteractWith Context triple: [angel, canInteractWith, humans]
-
A.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
-
B.
hasInteraction
chosen
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
C.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
canTakeActionWith
Indicates that one entity is able or permitted to perform an action jointly or in coordination with another entity.
-
E.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada269a9188190aada5b3799d4dfd7 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.