Triple
T10661672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levi-Civita symbol |
E251240
|
entity |
| Predicate | takesValues |
P93941
|
FINISHED |
| Object | +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: +1 | Statement: [Levi-Civita symbol, takesValues, +1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesValues Context triple: [Levi-Civita symbol, takesValues, +1]
-
A.
valuesIn
chosen
Indicates that one entity specifies or constrains the set of permissible values for another entity.
-
B.
multipleValuesAllowed
Indicates that the relationship or attribute can be associated with more than one value simultaneously, rather than being restricted to a single value.
-
C.
supportsValue
Indicates that one entity provides justification, evidence, or backing for the truth, relevance, or appropriateness of a particular value associated with another entity.
-
D.
normTakesValuesIn
Indicates that a norm or standard is defined such that its possible outcomes or assigned values lie within a specified set or range.
-
E.
catalogValue
Indicates that an entity has a specific value or entry as defined in a catalog or controlled list.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6e018d1e881909b8e62682104e842 |
completed | April 8, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.