Triple
T13035764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Géométrie descriptive |
E326556
|
entity |
| Predicate | but |
P42528
|
FINISHED |
| Object | établir systématiquement la géométrie descriptive |
—
|
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: établir systématiquement la géométrie descriptive | Statement: [Géométrie descriptive, but, établir systématiquement la géométrie descriptive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: but Context triple: [Géométrie descriptive, but, établir systématiquement la géométrie descriptive]
-
A.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
B.
to
chosen
Indicates a directional or goal-oriented relationship in which something is directed, transferred, or oriented toward a target or endpoint.
-
C.
in
Indicates that one entity is located within the spatial, temporal, or conceptual bounds of another entity.
-
D.
uso
Indicates that one entity uses, employs, or makes use of another entity for some purpose or function.
-
E.
bias
Indicates a systematic preference or prejudice in favor of or against an entity, affecting how it is treated, evaluated, or represented relative to others.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:55 p.m.