Triple
T36043213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ali (Ali & Ava) |
E1042597
|
entity |
| Predicate | sharesInterestWith |
P202420
|
FINISHED |
| Object | Ava (Ali & Ava) |
—
|
NE NERFINISHED |
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: Ava (Ali & Ava) | Statement: [Ali (Ali & Ava), sharesInterestWith, Ava (Ali & Ava)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesInterestWith Context triple: [Ali (Ali & Ava), sharesInterestWith, Ava (Ali & Ava)]
-
A.
shareStrategicInterestIn
Indicates that two or more entities have aligned or overlapping long-term goals or priorities regarding a particular issue, region, or domain.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
D.
sharesInteractionPointWith
Indicates that two entities have at least one common point or location at which they can interact or make contact with each other.
-
E.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
- F. None of above. chosen
Provenance (4 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
| PDg | Predicate description generation | batch_6a007dd263b48190bd5de5386d45858b |
completed | May 10, 2026, 12:45 p.m. |
Created at: May 3, 2026, 4:07 p.m.