Triple
T31463501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Sign Language |
E802664
|
entity |
| Predicate | usesSpaceGrammatically |
P187580
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Italian Sign Language, usesSpaceGrammatically, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSpaceGrammatically Context triple: [Italian Sign Language, usesSpaceGrammatically, yes]
-
A.
usesSpace
Indicates that one entity occupies, consumes, or makes use of physical or conceptual space associated with another entity.
-
B.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
C.
plaintextSpace
Indicates a relationship where text is represented or transmitted in an unencrypted, human-readable form with spaces preserved as literal characters.
-
D.
isWrittenWithoutSpace
Indicates that the referenced elements are written together as a single contiguous string, with no spaces between them.
-
E.
followsGrammaticalRule
Indicates that one entity conforms to or is consistent with a specified grammatical rule.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 30, 2026, 9:21 p.m.