Triple
T28672886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judas Coyne |
E725775
|
entity |
| Predicate | relationshipTypeWithFlorida |
P10690
|
FINISHED |
| Object | ex-girlfriend |
—
|
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: ex-girlfriend | Statement: [Judas Coyne, relationshipTypeWithFlorida, ex-girlfriend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithFlorida Context triple: [Judas Coyne, relationshipTypeWithFlorida, ex-girlfriend]
-
A.
relationshipToState
Indicates a relationship or connection that an entity has with a particular state or governmental body.
-
B.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
relationshipToStateLaw
Indicates how something is connected or subject to the provisions, requirements, or authority of a particular state law.
-
D.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
E.
relationshipTypeStart
Indicates the type or category of relationship that begins or is initiated at a specific point or event.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: April 28, 2026, 5:04 a.m.