Triple
T6849847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will o' the Wisp |
E157987
|
entity |
| Predicate | associatedWithWeightClass |
P8068
|
FINISHED |
| Object | featherweight |
—
|
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: featherweight | Statement: [Will o' the Wisp, associatedWithWeightClass, featherweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWeightClass Context triple: [Will o' the Wisp, associatedWithWeightClass, featherweight]
-
A.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
B.
weightClass
chosen
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
C.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
D.
associatedWithRank
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
E.
associatedWithClass
Indicates that an entity has a connection or linkage to a particular class or category, without specifying the exact nature of that relationship.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84acb288190a67d974197ecab2f |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.