Triple
T8486727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Content-Language |
E200848
|
entity |
| Predicate | multipleValuesAllowed |
P83554
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Content-Language, multipleValuesAllowed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multipleValuesAllowed Context triple: [Content-Language, multipleValuesAllowed, true]
-
A.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
B.
multipleUnit
Indicates that an entity is composed of or associated with more than one unit of the same type.
-
C.
canOperateInMultiple
Indicates that an entity is capable of functioning or being used across more than one context, environment, or mode.
-
D.
multipleAccess
Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
-
E.
canOperateInMultipleWith
Indicates that an entity is capable of functioning or being used concurrently within multiple instances, contexts, or configurations of 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.