Triple
T31704480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurosam |
E809141
|
entity |
| Predicate | hasLandApplication |
P196705
|
FINISHED |
| Object | SAMP/T |
—
|
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: SAMP/T | Statement: [Eurosam, hasLandApplication, SAMP/T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandApplication Context triple: [Eurosam, hasLandApplication, SAMP/T]
-
A.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
B.
hasLandOperations
Indicates that an entity conducts or is responsible for activities, services, or operations carried out on land.
-
C.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
D.
hasLandComponent
Indicates that something includes, consists of, or is associated with a land-based part or portion as one of its components.
-
E.
hasLandOffice
Indicates that an entity maintains or is associated with an official office responsible for managing land-related records, transactions, or administration.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: April 30, 2026, 11:13 p.m.