Triple
T18786079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langmuir monolayers |
E459378
|
entity |
| Predicate | areFormedAt |
P133008
|
FINISHED |
| Object | air–water interface |
—
|
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: air–water interface | Statement: [Langmuir monolayers, areFormedAt, air–water interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areFormedAt Context triple: [Langmuir monolayers, areFormedAt, air–water interface]
-
A.
formedAt
Indicates the time or date at which an entity was created, established, or came into existence.
-
B.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
-
C.
mayBeFormedWhen
Indicates that one entity has the potential to come into existence or be created as a result of another entity, condition, or process.
-
D.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
-
E.
dateFormedFrom
Indicates that one date value is derived or constructed from another date or date-related source.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978154ac819096356d2a488b45f0 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.