Triple
T21751989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean Marie Farina |
E536936
|
entity |
| Predicate | hasKeyAccord |
P145234
|
FINISHED |
| Object | fresh citrus |
—
|
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: fresh citrus | Statement: [Jean Marie Farina, hasKeyAccord, fresh citrus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyAccord Context triple: [Jean Marie Farina, hasKeyAccord, fresh citrus]
-
A.
hasAccord
Indicates that there is a formal agreement, harmony, or concord between the related entities.
-
B.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
C.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
-
D.
hasKeyAgency
Indicates that an entity serves as the primary responsible or controlling agency for another entity, action, or process.
-
E.
hasKeyBusiness
Indicates that one entity possesses or is associated with a primary or strategically important business of 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8a6d4881908cc69e7247cce3a5 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69f3ed4408190a4a78410bf660c44 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:50 p.m.