Triple
T3172449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mya |
E66384
|
entity |
| Predicate | relationshipFocus |
P46761
|
FINISHED |
| Object | modern dating |
—
|
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: modern dating | Statement: [Mya, relationshipFocus, modern dating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipFocus Context triple: [Mya, relationshipFocus, modern dating]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
relationshipDynamic
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
-
C.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
D.
relationshipPlannedWith
Indicates that a relationship between two entities has been intentionally arranged or scheduled to occur in the future.
-
E.
relationshipManaged
Indicates that one entity oversees, directs, or maintains responsibility for the ongoing management of a relationship involving 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada66da23c81908f063b44b48b1e53 |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada20880e481908ecac09d49b1f1c3 |
completed | March 8, 2026, 4:21 p.m. |
Created at: March 8, 2026, 3:06 p.m.