Triple
T2075542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dot Complicated |
E44912
|
entity |
| Predicate | authorBackground |
P938
|
FINISHED |
| Object | former Facebook marketing executive |
—
|
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: former Facebook marketing executive | Statement: [Dot Complicated, authorBackground, former Facebook marketing executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorBackground Context triple: [Dot Complicated, authorBackground, former Facebook marketing executive]
-
A.
authorOccupation
chosen
Indicates the professional role or job that an author holds or is associated with.
-
B.
authorOfDescription
Indicates that an entity is the creator or writer of a particular description or explanatory text about something.
-
C.
authorNationality
Indicates the relationship between an author and the country or nationality with which that author is identified.
-
D.
authorName
Indicates the name associated with the person or entity that authored a given work or resource.
-
E.
originAuthor
Indicates that an entity is the original creator or author of another entity (such as a work, document, or idea).
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba127dcc81909c2365d455eeb746 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.