Triple
T13743736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Seed (2.0) |
E330158
|
entity |
| Predicate | trackNumberOnPhrenology |
P110804
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [The Seed (2.0), trackNumberOnPhrenology, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackNumberOnPhrenology Context triple: [The Seed (2.0), trackNumberOnPhrenology, 11]
-
A.
numberOfGrooves
Indicates the count of grooves or channels present on or within an object or surface.
-
B.
estimatedNumberOfSkulls
Indicates the approximate count of skulls associated with an entity, based on estimation rather than an exact measurement.
-
C.
tonalSystem
Indicates a relationship where a language or musical system is characterized by a specific set of tonal patterns or pitch distinctions that structure its sounds or expressions.
-
D.
numberInInstrument
Indicates that an entity specifies the count or quantity of items contained within or associated with a particular instrument.
-
E.
phoneticValue
Indicates a relationship where a symbol, sign, or written element is associated with the specific sound or sequence of sounds it represents.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de020855ec8190a60fa1cb761f2e68 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:07 p.m.