Triple
T8566512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fancy Free |
E202814
|
entity |
| Predicate | characters |
P83677
|
FINISHED |
| Object | three sailors |
—
|
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: three sailors | Statement: [Fancy Free, characters, three sailors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characters Context triple: [Fancy Free, characters, three sailors]
-
A.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
B.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
C.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
characterTheme
Indicates that a particular theme, motif, or conceptual focus is associated with a given character.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d467c08190b2014d71ebbf8bbc |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:20 p.m.