Triple
T37249392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coehoorn system of fortification |
E923947
|
entity |
| Predicate | theorizedInWorkBy |
P114494
|
FINISHED |
| Object | Menno van Coehoorn |
—
|
NE NERFINISHED |
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: Menno van Coehoorn | Statement: [Coehoorn system of fortification, theorizedInWorkBy, Menno van Coehoorn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theorizedInWorkBy Context triple: [Coehoorn system of fortification, theorizedInWorkBy, Menno van Coehoorn]
-
A.
attestedInWorksOf
Indicates that something (such as a claim, form, or usage) is documented or evidenced within the works produced by a particular author or creator.
-
B.
theorizedInField
Indicates that a theory, idea, or hypothesis was formulated or developed within a particular academic or scientific field.
-
C.
discussedInWorkOf
Indicates that a subject is examined, treated, or talked about within a particular work or publication.
-
D.
theoryProposedByAuthor
chosen
Indicates that a particular theory was proposed or put forward by a specific author.
-
E.
theoryCoAuthor
Indicates that two or more entities jointly authored or contributed to the development of the same theory.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.