Triple
T21798125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabari |
E538155
|
entity |
| Predicate | relationshipTypeWithMeadow |
P10690
|
FINISHED |
| Object | romantic relationship |
—
|
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: romantic relationship | Statement: [Jabari, relationshipTypeWithMeadow, romantic relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithMeadow Context triple: [Jabari, relationshipTypeWithMeadow, romantic relationship]
-
A.
associationWithHumans
Indicates a general relationship, connection, or involvement between an entity and one or more humans.
-
B.
hasAgriculturalAssociation
Indicates that there exists a formal or recognized connection between an entity and an agricultural organization, group, or activity.
-
C.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
servesAsFarmSystemFor
Indicates that one entity functions as a developmental or feeder system that supplies trained or prepared resources (such as players, talent, or products) to another entity.
-
E.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f077fb87848190b6df9a9d1c5336af |
completed | April 28, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.