Triple
T11597151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Slate |
E275033
|
entity |
| Predicate | relationshipTypeWithFredFlintstone |
P10690
|
FINISHED |
| Object | boss-employee |
—
|
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: boss-employee | Statement: [Mr. Slate, relationshipTypeWithFredFlintstone, boss-employee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithFredFlintstone Context triple: [Mr. Slate, relationshipTypeWithFredFlintstone, boss-employee]
-
A.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
B.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
characterActorRelationship
Indicates a relationship where an actor portrays or is associated with a specific character in a work.
-
D.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
-
E.
fictionalRelationship
Indicates a relationship that exists only within a fictional or imagined context between entities.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89549c870819086e16e9110bbad87 |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.