Triple
T34769907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOEX Offshore 2007 |
E1002334
|
entity |
| Predicate | interestTypeInMacondo |
P77216
|
FINISHED |
| Object | leasehold interest |
—
|
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: leasehold interest | Statement: [MOEX Offshore 2007, interestTypeInMacondo, leasehold interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interestTypeInMacondo Context triple: [MOEX Offshore 2007, interestTypeInMacondo, leasehold interest]
-
A.
interestType
chosen
Indicates the specific category or nature of interest that one entity has in relation to another or to a subject.
-
B.
interestMayBe
Indicates that one entity potentially has an interest in, or may be interested in, another entity or subject.
-
C.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
D.
monarchInterestType
Indicates the type or category of interest or concern that a monarch has in relation to something.
-
E.
causeOfInterest
Indicates that one entity is the reason or source that brings about another entity’s interest or attention.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.