Triple
T6232991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teigen–Legend family |
E139399
|
entity |
| Predicate | documentedThrough |
P69655
|
FINISHED |
| Object | reality-style social media posts |
—
|
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: reality-style social media posts | Statement: [Teigen–Legend family, documentedThrough, reality-style social media posts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentedThrough Context triple: [Teigen–Legend family, documentedThrough, reality-style social media posts]
-
A.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
B.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
C.
legacyDocumentedBy
Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
-
D.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
E.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
- 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062efa25c8190a54f5a6f5b5ad24f |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:22 p.m.