Triple
T9812150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Taylor |
E238297
|
entity |
| Predicate | relationshipDuration |
P47544
|
FINISHED |
| Object | about 8 years |
—
|
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: about 8 years | Statement: [Brian Taylor, relationshipDuration, about 8 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipDuration Context triple: [Brian Taylor, relationshipDuration, about 8 years]
-
A.
relationshipDurationWith
chosen
Indicates the length of time that a specified relationship between two entities has existed or is expected to last.
-
B.
marriageDuration
Indicates the length of time that a marriage relationship has existed between two spouses.
-
C.
relationshipOutcome
Indicates the result or consequence that arises from a particular relationship between two or more entities.
-
D.
romanticRelationshipStatus
Indicates the nature or state of a romantic relationship between entities, such as whether they are dating, committed, separated, or otherwise romantically involved.
-
E.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb222ba788190a9085272a3de7852 |
completed | April 2, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:30 p.m.