Triple
T16492906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Composite fermion |
E400608
|
entity |
| Predicate | hasFillingFactorMapping |
P123744
|
FINISHED |
| Object | ν = p/(2p±1) |
—
|
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: ν = p/(2p±1) | Statement: [Composite fermion, hasFillingFactorMapping, ν = p/(2p±1)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFillingFactorMapping Context triple: [Composite fermion, hasFillingFactorMapping, ν = p/(2p±1)]
-
A.
hasFillingType
Indicates that an entity is associated with a specific type or category of filling it contains or uses.
-
B.
hasFillingSystem
Indicates that an entity is equipped with or uses a particular filling system or mechanism.
-
C.
hasOfficialMapping
Indicates that there exists an established, authoritative correspondence or translation between one entity and another.
-
D.
mayBeFilledBy
Indicates that one entity has the potential or permission to be occupied, completed, or satisfied by another entity.
-
E.
isTypicallyFilledWith
Indicates that one entity is commonly or usually occupied, loaded, or contained by another entity.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e30cb648190a52cb32896c4ac5a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:13 a.m.