Triple
T36468607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenchel–Nielsen coordinates |
E898483
|
entity |
| Predicate | numberOfLengthParameters |
P204885
|
FINISHED |
| Object | 3g - 3 + n |
—
|
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: 3g - 3 + n | Statement: [Fenchel–Nielsen coordinates, numberOfLengthParameters, 3g - 3 + n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfLengthParameters Context triple: [Fenchel–Nielsen coordinates, numberOfLengthParameters, 3g - 3 + n]
-
A.
parameterCount
Indicates the number of parameters associated with a given function, method, or callable entity.
-
B.
numberOfParametersOfLargestVariant
Indicates the total count of parameters in the variant that has the greatest number of parameters among all variants of an entity.
-
C.
parameterCountRelativeTo
Indicates a relationship comparing the number of parameters of one entity (such as a function, method, or operation) to that of another entity.
-
D.
argumentCount
Indicates the number of arguments that a function, method, or callable entity takes.
-
E.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.